Do It, Delegate It, Defer It

“Do It, Delegate It, Defer It” names the three choices available once a next action has been identified: complete it now when it takes less than two minutes, delegate it when someone else is better suited to the task, or defer it by placing it in an organization system as work to do later. The expression is a compact decision rule for turning an acknowledged commitment into an immediate response, a transfer of responsibility, or a tracked future action. Its significance lies not in promising that every task will be done, but in preventing an undefined or forgotten task from quietly remaining unresolved.

The decision point

The rule begins only after the work has been clarified into a next action. Deciding what to do is not itself an action in the relevant sense: a decision does not take time in the way a physical activity does. To move a project toward a decision, one may need to obtain external information, such as asking someone for input on a proposal, or do internal preparatory work, such as drafting ideas for a reorganization. Either route still calls for a concrete next step. Once that step is identified, the three options establish what happens to it.

The options distinguish different circumstances rather than ranking all work by importance. The immediate-completion choice applies when the action takes under two minutes. Delegation applies when the person handling the item is not the most appropriate person to perform its next action. Deferral applies when the action belongs in the later-work system rather than being done now or assigned elsewhere. Together, the choices close the gap between recognizing that something needs attention and deciding how it will be handled.

Immediate completion and the two-minute threshold

The two-minute threshold is a practical trigger for doing a small action at the point when the item is first picked up. The examples are deliberately ordinary: a memo may need only a thirty-second read and a quick yes-or-no or other response on a note attached for the sender; a catalog may be browsed briefly and then discarded, routed, or filed as reference; a quick message may be left on someone’s voicemail. In each case, postponing the action would preserve a small open task that could instead be finished during processing.

This option is not a claim that all short tasks deserve priority over larger work. It is tied to the moment of handling the item and to the modest duration specified by the rule. The contrast is with treating every incoming item as an invitation to delay without deciding what it requires. An action short enough to complete immediately need not be converted into another reminder, while work that cannot be completed under the threshold must be handled through delegation or deferral.

Delegation, ownership, and communication

Delegation is the appropriate branch when the current handler is not the best person to carry out the action. It therefore turns processing into a decision about responsibility, not merely a decision about the handler’s own to-do list. The book’s account of contemporary work gives that distinction organizational weight: many outcomes depend on cross-divisional communication and cooperation, while office silos give way to shared messages and requests. In that environment, transferring a task is useful only if the request reaches a system where it can be processed and considered for action.

The rule’s effectiveness consequently depends on dependable communication practices. A request or relevant information sent by voicemail, email, conversation, or written note must enter the recipient’s system, be processed and organized, and remain available for review as an action option. If a recipient reliably manages voicemail but not email or paper, the sender is forced to use only the recipient’s trusted medium. The text treats that limitation as a needless obstruction to getting work done with the least effort. Delegation is not complete as a practical arrangement merely because responsibility has been spoken aloud; the handoff must survive in a system that the recipient will review.

Deferral and contextual reminders

To defer an action is not to abandon it or leave it vaguely in the future. It is to place it in an organization system as an option for later work. The calendar is reserved for the hard landscape of fixed commitments; most actions that should be done as soon as possible, but not on a definite day or at a definite time, belong elsewhere. This division protects the calendar from becoming a fragile wish list whose postponed tasks must be carried from day to day.

For these as-soon-as-possible actions, the book recommends organizing reminders by the context required to complete them: the tool, location, or person involved. A computer task belongs on an “At Computer” list; a bank stop or hardware-store visit belongs under “Errands”; a face-to-face conversation with a partner named Emily can be tracked in an “Emily” folder or list. The needed degree of separation depends on the number of actions being tracked and how often a person moves between contexts. One list may suffice for someone with only twenty-five next actions, whereas fifty or a hundred mixed tasks can make a single list difficult to scan and force repeated, unproductive sorting.

Context is also a test of whether the next action has been made concrete enough. At any given moment, the first question is what can be done where one is, with the tools and people available. A person in traffic with a phone may be able to act only on calls; an action requiring a store, a computer, or a face-to-face conversation must wait for its appropriate setting. Context-based lists reduce repeated reconsideration by exposing the actions that are possible now and hiding those that cannot yet be done. They also force the handler to identify the physical action before filing it: a catchall “Misc.” list can let an item remain vague instead of resolving what actually needs to happen next.

The rule’s wider conditions

The three choices answer a problem created by work that no longer has the clear edges of plowing fields, packing boxes, or milking cows. Many projects can be improved indefinitely, and a practically limitless quantity of potentially relevant information is accessible through the Web. Cross-divisional outcomes require communication and cooperation, while organizations continually change their goals, products, partners, customers, markets, technologies, and owners. Individual professionals also change roles and careers. The resulting flow of external information and internal ideas and agreements produces commitments that are difficult to manage without a system operating from large outcomes down to small open details.

In that setting, “Do It, Delegate It, Defer It” is a local decision mechanism within a broader effort to maintain control. It does not simplify a person’s aims or reduce the amount that may need doing. It makes the disposition of a particular next action explicit, while collection and review preserve the information needed to act on it. A person cannot renegotiate an agreement with themselves if they cannot remember making it, nor renegotiate agreements with others after losing track of them. The three-way choice is therefore a practical hinge between capturing a commitment and keeping it available for completion, transfer, or later reconsideration.

The rule also presupposes that an organization can tolerate the fact that no one can do everything. People need to be able to renegotiate what they are not doing, and that requires commitments to remain visible rather than disappear between conversations and inboxes. A shared standard of collecting all incoming commitments does not guarantee that a group is pursuing the right goals or even that it is on the right “ship”; it does make the group’s chosen direction more energetically manageable. The expression’s force is modest but consequential: each clarified action must be completed, handed to the right person, or retained in a trusted system, rather than left to occupy attention as an untracked obligation.